@ekohl do you have an idea why the test:<plugin> test seems to be flaky? (see attempts in https://github.com/dm-drogeriemarkt/foreman_dlm/actions/runs/9001612772?pr=67 ). Re-running the tests without any change fixes the problem.

Looks like the same problem again, bit I don't see any error. This plugin is the only one with acceptance tests using Capybara. Maybe we hit a caching or concurrency problem in Github actions?

AFAIK the test order is randomized. If you pass seed 3970 then perhaps you can reproduce it locally?

AFAIK the test order is randomized. If you pass seed 3970 then perhaps you can reproduce it locally?

Running the tests with DEBUG_JS_TEST=1 shows more information and reveals:

[MinitestRetry] retry 'test_0001_the index page works' count: 1,  msg: Selenium::WebDriver::Error::SessionNotCreatedError: session not created: Chrome failed to start: exited normally.
  (session not created: DevToolsActivePort file doesn't exist)
  (The process started from chrome location /opt/google/chrome/chrome is no longer running, so ChromeDriver is assuming that Chrome has crashed.)
    test/integration_test_helper.rb:302:in `login_admin'
    test/test_helper.rb:84:in `before_setup'
    test/integration_test_helper.rb:331:in `before_setup'

I found a similar issue here: SeleniumHQ/selenium#12841